\section{Introduction} 
\subsection{Context}

\SM{} is a local project in HAG. To start our work on the right way,
we tried to define what is the need of \MIS{} and why this kind of
project was initiated.

To provide the right results we need to answer 5 important questions:

\begin{description}
\item[Why System Map?]
Make a landscape of Information System of company consists to identify
all systems used on this site and relations between these
systems. It's important to adapt this kind of work to company
needs. This work will give as a result the tool to help the Business
and \MIS{} in IT strategy.\\

\item[How to start?]
The project of urbanisation starts with inventory of existing
functional systems (applications) and data streams exchanged among
these systems. This is the stage of application maps creation (logic
view). The other step is the infrastructure map (physic view), which
covers the databases, network and technical elements. The purpose is
to have graphical representation of all parts of our Information
System and the links between them.\\

\item[What are the principal steps of urbanisation project?]
The map of Information System will allow us to fix the goals of
urbanisation plan. They will be classified by priorities in relation
to company's IT strategy. For us these objectives are described later
in this document.\\

\item[Who must be involved?]
To have more complete map of our Information System, we defined the
stakeholders, with whom we discussed about their needs and roles. About
working team see section~\ref{sec:an_sm_spec_project_organisation}.\\

\item[Which tool will we use?]
To have the first results as soon as possible and do the job in a
pragmatic approach we will use \tsf{MS Visio} and
we will build 3 layers map (application; infrastructure; link between
application and infrastructure). The second objective of our project
is to find a tool, which will allow us more powerful management of our
system map than simple \tsf{Visio} drawing.
\end{description}

On the HAG site, both \MIS{} and Business don't have a clear view of
the infrastructure and applications they use. Sometimes, applications
are obsoletes and nobody knows about that because of historical
reasons. Other applications cost a lot (licence, maintenance) and are
not really as important as in the past and can be replaced by another
solutions, such as global applications.

Nobody can quickly identify with precision the resources an
application requires and use to work properly. Nobody can say if
hardware fails which applications will be impacted.

\subsection{Goals of \SM{}}
The main goal is to provide a complete map of infrastructure and
applications that are used in HAG. Then, the project help us to
identify the applications and try to determine if they are useful or
not, try to move them from local to global if necessary. 

Secondly, to provide a good visibility of our IT systems in order to
be more reactive and effective in front of business requests. To be
able to give them a good view of the applications they use regarding
their business area. 

\MIS{} do not have any idea of what Business is doing himself, and
with \SM{} this is a way, \MIS{} can imply them more than today
to work together and be more proactive (e.g. to determine how much
internet band width must be increased in the next periods).

\subsection{Project organisation}
\label{sec:an_sm_spec_project_organisation}
New joiners in \MIS{} infrastructure and application teams (Tea,
Giorgi and Jean-Christophe) are in charge of this project. This is
their responsibility and they report to Guillaume \tsc{Doriry} and
Dickie \tsc{Davies}. The project starts in March 2007 and continues to
August 2007.

\subsection{Environnement}
The useful information to build the map mainly comes from \tsf{AKIM}
reference, but also from key/experimented users. Moreover, everybody
in the two teams can provide a part of the information we need.

\section{Project description}
\subsection{Existing}
For STD and DOE sites, \SM{} as \tsf{Visio} diagrams already
exists. Firstly, the project team has to work in the same way, in order
to provide a similar document. As decided, this document will not be
the final output, because of maintainability. So the team does this
work in order to gain experience and be more familiar with the
environment.\\

\tsf{AKIM interface database} and \tsf{AKIM reference} are two Notes
database where useful information can be extracted to do the job.

A tool to discover the infrastructure's architecture is available from
\tsf{BIS team}. It can help the project team to build the infrastructure
layer.

\subsection{Limits}
In terms of application, the limit is clear: all of them that are used
in HAG must be drawn in the map, either they are local, regional or
global.

Concerning infrastructure, all parts of the infrastructure that are
used by one of the previous applications must be drawn on the map.

\subsection{Constraints}
The team must use \tsf{Microsoft Visio} to provide the maps.

\section{What is expected}
\subsection{Output}
A complete map, using \tsf{Microsoft Visio}, with two different views
is expected from the project team:
\begin{itemize}
\item An application layer with different codes to identify the
business area and other codes to identify if they are active or
inactive. Each application must be provided with its interfaces with
others.
\item An infrastructure layer with different colours to identify
equipment's location.
\end{itemize}






